Comments
-
Thanks so much for taking the time to answer. What would this Bi-Directional Policy look like? The Non-SonicWall Site (3) has limited options unfortunately. They would not do a VPN and only opened the port to the static public IP of Site 2 and would not allow for anything else. Thanks again.
-
Just in case it happens to another person: It ended up being the cable that connected the main Frontier ONT to the TZ400. Frontier techs have been giving out these "CAT6" white flat cables that don't seem to be of high quality. Replaced with a high quality CAT6 patch cable and all errors and disconnects went away.
-
Forgot to mention, X1 is connected to Frontier FIOS Modem/Router (Fiber Optic Internet Service).
-
No. I have tried every combination possible, including app passwords in Gmail, trying other email providers, SSL, TLS, different ports and nothing works. I still get the same error message.
-
Thanks for the reply but I don't want this changed for all Rules. Besides, the setting itself tells you that you should be able to override this default timeout by setting the timeout in the individual rule, yet it doesn't.
-
Hoping this is the true cause and solution although it wasn't a reboot cycle what I experienced. Thanks so much for passing along the information!
-
What is the current Firmware on your SOHO? Also, have you tried re-creating the user, or creating a new test user and assigning the correct Groups and VPN Access? You may also try, as a test, giving access to the LAN Subnets instead of a specific IP or Address Object.
-
Having the same problem on a TZ 370 with SonicOS 7.0.1-5023-R1826. How did you solve the problem?
-
I know this is a year old but having the same problem on NSA 240, NSA 250m, NSA 2400 which were working until the 5.9.2.13-7o upgrade. These firewalls will be decommissioned but in the meantime the Email alerts are important.